Assessor Resource

ICTPRG510
Maintain custom software

Assessment tool

Version 1.0
Issue Date: May 2024


This unit describes the skills and knowledge required to maintain software so that it continues to meet client user requirements.

It applies to individuals who may work as programmers who are required to maintain existing software.

No licensing, legislative or certification requirements apply to this unit at the time of publication.

You may want to include more information here about the target group and the purpose of the assessments (eg formative, summative, recognition)


Evidence Required

List the assessment methods to be used and the context and resources required for assessment. Copy and paste the relevant sections from the evidence guide below and then re-write these in plain English.

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Determine the software fault to be corrected

1.1 Collect and review the software fault details from sources

1.2 Obtain technical data to assist in identifying the problem

1.3 Clarify nature of the problem with appropriate person where necessary

2. Identify and isolate the fault

2.1 Review program documentation for specific modules in order to pinpoint problem areas

2.2 Review the source code for logic errors

2.3 Read manuals, help files and 'read me files' to determine if there is a known fix

2.4 Undertake additional testing to identify or duplicate fault

2.5 Escalate the difficult faults that cannot be identified

3. Design a fix for the fault

3.1 Ensure that the requirements needed to fix the fault are understood by the client

3.2 Consider alternative options and choose the most effective solution

3.3 Consider the possible impact of the fix on other parts of the system

3.4 Document the changes according to the organisational guidelines

4. Carry out the fix to the software

4.1 Identify, and obtain, access to the appropriate software development tools, source code, and libraries

4.2 Construct the appropriate code to correct the fault, according to organisational and programming standards

4.3 Compile, or regenerate, the code for changed programs and the associated modules

4.4 Correct, and resubmit, the code until error free

4.5 Document the changes, according to organisational and programming standards

5. Test the fix and associated system areas

5.1 Check logic to ensure that it works with test data, corrects original fault, and does not cause problems elsewhere

5.2 Request users to perform acceptance testing and record outcomes

6. Hand over to systems operations area

6.1 Update the documentation to reflect all the changes made

6.2 Confirm acceptance by systems operations and arrange for sign-off, according to procedures

Evidence of the ability to:

effectively maintain custom software

apply a fix that works

deploy a possible range of solutions to produce the same results.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

explain the concepts relating to analysing a system performance compared with the system’s current functionality

describe the processes and procedures relating to testing software systems

describe current industry-accepted hardware and software products, as they relate to system maintenance

specify the programming code required for the project

describe the program documentation required

describe the impact of changes on applications and systems

identify and summarise the programming standards relating to custom software.

Gather evidence to demonstrate consistent performance in conditions that are safe and replicate the workplace. Noise levels, production flow, interruptions and time variances must be typical of those experienced in the programming and software development industry, and include access to:

the fault logs, and help-desk reports

software development tools, documentation and environment

source code and libraries

the appropriate learning and assessment support.

Assessors must satisfy NVR/AQTF assessor requirements.

Submission Requirements

List each assessment task's title, type (eg project, observation/demonstration, essay, assingnment, checklist) and due date here

Assessment task 1: [title]      Due date:

(add new lines for each of the assessment tasks)

Assessment Tasks

Copy and paste from the following data to produce each assessment task. Write these in plain English and spell out how, when and where the task is to be carried out, under what conditions, and what resources are needed. Include guidelines about how well the candidate has to perform a task for it to be judged satisfactory.

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Determine the software fault to be corrected

1.1 Collect and review the software fault details from sources

1.2 Obtain technical data to assist in identifying the problem

1.3 Clarify nature of the problem with appropriate person where necessary

2. Identify and isolate the fault

2.1 Review program documentation for specific modules in order to pinpoint problem areas

2.2 Review the source code for logic errors

2.3 Read manuals, help files and 'read me files' to determine if there is a known fix

2.4 Undertake additional testing to identify or duplicate fault

2.5 Escalate the difficult faults that cannot be identified

3. Design a fix for the fault

3.1 Ensure that the requirements needed to fix the fault are understood by the client

3.2 Consider alternative options and choose the most effective solution

3.3 Consider the possible impact of the fix on other parts of the system

3.4 Document the changes according to the organisational guidelines

4. Carry out the fix to the software

4.1 Identify, and obtain, access to the appropriate software development tools, source code, and libraries

4.2 Construct the appropriate code to correct the fault, according to organisational and programming standards

4.3 Compile, or regenerate, the code for changed programs and the associated modules

4.4 Correct, and resubmit, the code until error free

4.5 Document the changes, according to organisational and programming standards

5. Test the fix and associated system areas

5.1 Check logic to ensure that it works with test data, corrects original fault, and does not cause problems elsewhere

5.2 Request users to perform acceptance testing and record outcomes

6. Hand over to systems operations area

6.1 Update the documentation to reflect all the changes made

6.2 Confirm acceptance by systems operations and arrange for sign-off, according to procedures

Evidence of the ability to:

effectively maintain custom software

apply a fix that works

deploy a possible range of solutions to produce the same results.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

explain the concepts relating to analysing a system performance compared with the system’s current functionality

describe the processes and procedures relating to testing software systems

describe current industry-accepted hardware and software products, as they relate to system maintenance

specify the programming code required for the project

describe the program documentation required

describe the impact of changes on applications and systems

identify and summarise the programming standards relating to custom software.

Gather evidence to demonstrate consistent performance in conditions that are safe and replicate the workplace. Noise levels, production flow, interruptions and time variances must be typical of those experienced in the programming and software development industry, and include access to:

the fault logs, and help-desk reports

software development tools, documentation and environment

source code and libraries

the appropriate learning and assessment support.

Assessors must satisfy NVR/AQTF assessor requirements.
Copy and paste from the following performance criteria to create an observation checklist for each task. When you have finished writing your assessment tool every one of these must have been addressed, preferably several times in a variety of contexts. To ensure this occurs download the assessment matrix for the unit; enter each assessment task as a column header and place check marks against each performance criteria that task addresses.

Observation Checklist

Tasks to be observed according to workplace/college/TAFE policy and procedures, relevant legislation and Codes of Practice Yes No Comments/feedback
Collect and review the software fault details from sources 
Obtain technical data to assist in identifying the problem 
Clarify nature of the problem with appropriate person where necessary 
Review program documentation for specific modules in order to pinpoint problem areas 
Review the source code for logic errors 
2.3 Read manuals, help files and 'read me files' to determine if there is a known fix 
Undertake additional testing to identify or duplicate fault 
Escalate the difficult faults that cannot be identified 
Ensure that the requirements needed to fix the fault are understood by the client 
Consider alternative options and choose the most effective solution 
Consider the possible impact of the fix on other parts of the system 
Document the changes according to the organisational guidelines 
Identify, and obtain, access to the appropriate software development tools, source code, and libraries 
Construct the appropriate code to correct the fault, according to organisational and programming standards 
Compile, or regenerate, the code for changed programs and the associated modules 
Correct, and resubmit, the code until error free 
Document the changes, according to organisational and programming standards 
Check logic to ensure that it works with test data, corrects original fault, and does not cause problems elsewhere 
Request users to perform acceptance testing and record outcomes 
Update the documentation to reflect all the changes made 
Confirm acceptance by systems operations and arrange for sign-off, according to procedures 

Forms

Assessment Cover Sheet

ICTPRG510 - Maintain custom software
Assessment task 1: [title]

Student name:

Student ID:

I declare that the assessment tasks submitted for this unit are my own work.

Student signature:

Result: Competent Not yet competent

Feedback to student

 

 

 

 

 

 

 

 

Assessor name:

Signature:

Date:

Assessment Record Sheet

ICTPRG510 - Maintain custom software

Student name:

Student ID:

Assessment task 1: [title] Result: Competent Not yet competent

(add lines for each task)

Feedback to student:

 

 

 

 

 

 

 

 

Overall assessment result: Competent Not yet competent

Assessor name:

Signature:

Date:

Student signature:

Date: